Skip to content

Conversation

@aaron-skydio
Copy link
Contributor

Building symenginepy as part of the SymForce build, I get an error currently if I try to build under a source directory with a space in the path:

[100%] Linking CXX shared library symengine_wrapper.cpython-38-x86_64-linux-gnu.so
c++: error: test/build/symenginepy-prefix/src/symenginepy-build/build/lib.linux-x86_64-cpython-38/symengine/lib/version_script_symengine_wrapper.txt: No such file or directory
make[5]: *** [symengine/lib/CMakeFiles/symengine_wrapper.dir/build.make:121: symengine/lib/symengine_wrapper.cpython-38-x86_64-linux-gnu.so] Error 1
make[4]: *** [CMakeFiles/Makefile2:132: symengine/lib/CMakeFiles/symengine_wrapper.dir/all] Error 2
make[3]: *** [Makefile:136: all] Error 2
error: error building project
make[2]: *** [CMakeFiles/symenginepy.dir/build.make:86: symenginepy-prefix/src/symenginepy-stamp/symenginepy-build] Error 1

This change seems to fix that. I'm not 100% sure in what scenarios this applies to a standalone build of symengine? But I figured I'd open a PR and propose this change

Coming from here on the SymForce repo: symforce-org/symforce#414

Building symenginepy as part of the SymForce build, I get an error currently if I try to build under a source directory with a space in the path:

```
[100%] Linking CXX shared library symengine_wrapper.cpython-38-x86_64-linux-gnu.so
c++: error: test/build/symenginepy-prefix/src/symenginepy-build/build/lib.linux-x86_64-cpython-38/symengine/lib/version_script_symengine_wrapper.txt: No such file or directory
make[5]: *** [symengine/lib/CMakeFiles/symengine_wrapper.dir/build.make:121: symengine/lib/symengine_wrapper.cpython-38-x86_64-linux-gnu.so] Error 1
make[4]: *** [CMakeFiles/Makefile2:132: symengine/lib/CMakeFiles/symengine_wrapper.dir/all] Error 2
make[3]: *** [Makefile:136: all] Error 2
error: error building project
make[2]: *** [CMakeFiles/symenginepy.dir/build.make:86: symenginepy-prefix/src/symenginepy-stamp/symenginepy-build] Error 1
```

This change seems to fix that.  I'm not 100% sure in what scenarios this applies to a standalone build of symengine?  But I figured I'd open a PR and propose this change

Coming from here on the SymForce repo: symforce-org/symforce#414
Copy link
Contributor

@certik certik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @aaron-skydio thanks for the fix! Great catch.

@aaron-skydio
Copy link
Contributor Author

Thanks for the quick approve! I'm not sure if the CI failures are related to my change or not? It doesn't really look like it superficially but of course I'm not entirely sure

@certik certik merged commit b5bd3fe into symengine:master Dec 21, 2024
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants